Central Irrigation Control System

ABSTRACT

In one embodiment of the present invention, irrigation software is provided for an irrigation system. The irrigation software may include a hierarchical watering plan display, water pump adjustment, water pump efficiency profile use, a soil moisture interface, a historical flow interface, a demand ET interface, an instant program interface, an instant program interface, a manual irrigation interface, a precipitation management group interface, a rain schedule adjustment algorithm, a map-to-monitor button, a universal start time shift interface, and a conditional screen saver.

RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/292,148 filed Mar. 4, 2019 entitled CentralIrrigation Control System, which is a continuation of and claimspriority to U.S. patent application Ser. No. 14/923,266 filed Oct. 26,2015 entitled Central Irrigation Control System (now U.S. Pat. No.10,231,391 Issued Mar. 19, 2019), which is a continuation of and claimspriority to U.S. patent application Ser. No. 13/208,249 filed Aug. 11,2011 entitled Central Irrigation Control System (now U.S. Pat. No.9,192,110 Issued Nov. 24, 2015), which claims benefit of and priority toU.S. Provisional Application Ser. No. 61/372,814 filed Aug. 11, 2010entitled Central Irrigation Control System, the contents of all of whichare incorporated in their entireties herein.

BACKGROUND OF THE INVENTION

Large irrigation systems typically include a central irrigationcontroller that is responsible for a variety of tasks associated withoperation of the irrigation system. Such central controllers aretypically software-based systems executed on a local computer system.

The central controller software is typically responsible for planningwatering schedules and monitoring operation of the irrigation system.Watering commands or irrigation schedules are typically communicated toa plurality of satellite controllers at various locations on the site.The satellite controllers are connected to valves either in each of thesprinklers or a valve connected to sprinklers or groups sprinklers andcan thereby direct each of the sprinklers to water according to thewatering schedule.

SUMMARY OF THE INVENTION

In one embodiment of the present invention, irrigation software isprovided for an irrigation system. The irrigation software may include ahierarchical watering plan display, water pump adjustment, water pumpefficiency profile use, a soil moisture interface, a historical flowinterface, a demand evapotranspiration (ET) interface, an instantprogram interface, a manual irrigation interface, a precipitationmanagement group interface, a rain schedule adjustment algorithm, amap-to-monitor button, a universal start time shift interface, and aconditional screen saver.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects, features and advantages of which embodiments ofthe invention are capable of will be apparent and elucidated from thefollowing description of embodiments of the present invention, referencebeing made to the accompanying drawings, in which:

FIG. 1 illustrates an irrigation system for use with the presentinvention.

FIG. 2 illustrates a view of an irrigation software display according toa preferred embodiment of the present invention.

FIG. 3 illustrates a flow chart for navigating a hierarchical interfaceaccording to the present invention.

FIG. 4 illustrates a flow chart for navigating a hierarchical interfaceaccording to the present invention.

FIG. 5 illustrates a flow chart for navigating a hierarchical interfaceaccording to the present invention.

FIG. 6 illustrates a view of an irrigation software display according toa preferred embodiment of the present invention.

FIG. 7 illustrates a view of a water pump station in communication witha server according to the present invention.

FIG. 8 illustrates a flow chart of a method for monitoring and usingefficiency profiles for a water pump.

FIG. 9 illustrates a view of an irrigation software display according toa preferred embodiment of the present invention.

FIG. 10 illustrates a view of an irrigation software display accordingto a preferred embodiment of the present invention.

FIG. 11 illustrates a view of an irrigation software display accordingto a preferred embodiment of the present invention.

FIG. 12 illustrates a view of an irrigation software display accordingto a preferred embodiment of the present invention.

FIG. 13 illustrates a view of an irrigation software display accordingto a preferred embodiment of the present invention.

FIG. 14 illustrates a view of i an irrigation software display accordingto a preferred embodiment of the present invention.

FIG. 15 illustrates a method of recalculating irrigation schedule runtimes according to the present invention.

FIGS. 16 and 17 illustrate a computer monitor and a screen saveraccording to the present invention.

DESCRIPTION OF EMBODIMENTS

Specific embodiments of the invention will now be described withreference to the accompanying drawings. This invention may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of the invention to those skilled in the art. Theterminology used in the detailed description of the embodimentsillustrated in the accompanying drawings is not intended to be limitingof the invention. In the drawings, like numbers refer to like elements.

FIGS. 1-16 illustrate various aspects of irrigation control softwareaccording to the present invention. Preferably, this control software islocated on and executable by a computer. FIG. 1 illustrates an exampleirrigation system 10 having a central irrigation server 12, such as aPC, which is in communication (e.g., wired or wireless) with a pluralityof satellite controllers 14. Each satellite controller is connected to avalve in a sprinkler 16, thereby directly controlling when eachsprinkler 16 waters. The central irrigation server 12 communicateswatering schedule information to the appropriate satellite controller 14and the satellite controller 14 operates its connected sprinklers 16according to this watering schedule.

The central irrigation server 12 may alternately operate over a two-wireencoder/decoder network in which the server 12 is directly connected toeach sprinkler 16 via two wires, as is known in the art. These wiresprovide power and communication signals for a decoder at each sprinklervalve. In this respect, each sprinkler 16 is directly controlled.

Preferably, the irrigation control software is executed by the centralirrigation server 12 and stores data (e.g., in a database) in a locallyattached storage device. Alternately, the irrigation control softwarecan be executed and stored on a remote server and displayed on thecentral irrigation server 12 via a webpage over the internet.

Hierarchical Watering Plan Display

FIG. 2 illustrates a watering plan interface 100 of the central controlsoftware that uses a hierarchical display to provide both top-level orsummary information and more detailed information about specificwatering programs or schedules. More specifically, the watering planinterface allows for selectable visual expansion of varioussubcategories of an irrigation program.

In the specific example shown in FIG. 2, the watering plan action isselected from the action menu 102, which causes the watering planinterface 104 to display. The interface 104 includes a top-levelinformation display 103 for each program comprising a plurality ofinformation or control columns 108. For example, these columns mayinclude a program name, program number, auto cycle control, lastruntime, last inches of water applied, next inches of water to beapplied, percentage adjust, program start time, priority level, activedays, run time calculation adjustments, evapotranspiration mode,evapotranspiration source, reference evapotranspiration value, rainfallamount and a soil moisture sensor value (e.g., from a Turf Guard™sensor).

The top level information display 103 also includes a “plus/minus”expansion symbol 110 that allows the user to expand or hidesubcategories of the main program (e.g., the plus symbol indicates thatexpansion can occur and the minus symbol indicates that a subcategory isexpanded). In the example of FIG. 2, the first subcategory tier 105illustrates geographic areas that are watered with the program, such asholes of a golf course. This first subcategory tier 103 preferablyincludes the same or similar columns 108 as the top level program 103.Additionally, each first subcategory tier 105 can include its ownselectively expandable second subcategory tier 107, which, in thepresent example, refers to individual sprinklers residing on theselected hole, a sub set of the selected area.

While not shown, it is possible to add yet additional expandablesubcategories under each station displaying information for eachsprinkler connected to a specific satellite station. For example,sprinkler column information may include a sprinkler popup indicator,nozzle rotation indicator and a sprinkler water flow indicator.

As seen in the operation flow chart of FIG. 3, the user clicks on the“plus” sign 110 next to a specific top level category 103 program name120. This action causes the software to display a list of geographicsubcategories in the first subcategory tier 105 beneath the top levelcategory program name, including information and control columns 108associated with the subcategory entries 122. The user clicks on the“plus” 110 next to a geographic subcategory name 124. This action causesthe software to display a list of sprinklers beneath the geographicsubcategory entry in the second subcategory tier 107, includinginformation and control columns 108 associated with each entry 126.

As best seen in FIG. 2, the top level program information also includesa colored indicator 112A and 112B that identifies problems or properfunctioning of an irrigation program. In the example of FIG. 2, a whiterain drop-shaped indicator 112A indicates proper functionality and ablack rain drop-shaped indicator 112B indicates a problem with theirrigation schedule or various components. The indicators 112A and 1126may alternately display a solid color, such as green or red, or a mixedcolor, such as part green and part red.

In this respect, the top level indicator can indicate if all areas andstations in the subcategories beneath it are operating properly (e.g.,color is all green or white 112A), one or more stations have errors orfailed to water (e.g., color is partially green and red or black andwhite), or all areas and stations have errors or failed to water (e.g.,color is all red). Each sub category can have similar indicators,identifying errors or proper functioning of that specific subcomponent.Thus, a user can selectively view each subcategory to determine where anerror warning is being generated.

As seen in the operational flow chart of FIG. 4, a problem with acomponent of the irrigation system 10 used in an irrigation schedulecauses the software to display a mixed green and red color in the raindrop-shaped indicator 112, seen in 130. In 132, the user clicks on theplus expansion symbol 110 of the top level tier 103 to expand the firstsubcategory tier 105. In 134, the user reviews the geographic areas ofthe first subcategory tier 105 and determines which areas have a red orproblem indicator 112 associated with them. In 136, the user expands thesprinkler subcategory of the second subcategory tier 107 and in 138reviews stations or sprinklers that have a red or problem indicator 112.Once the stations or sprinklers with errors have been identified by theuser, corrective action can be performed to address the problem.

Water Pump Adjustments

FIG. 6 illustrates a water pump adjustment interface 150 that displayswater pump usage graphs 152 and adjustable limits 154 (e.g., sliders) onthe amount of water flow a pump can deliver. The sliders 154 of the pumppreferably display a percentage of the pump output 156, a limit amountin gallons per minute 158 and an electricity amount in kilowatts perhour 159. Hence, the user can limit a pump output based on water flowand or electricity usage.

As seen in FIG. 7 and the flow chart of FIG. 8, the central controllerserver is preferably connected to a water pump station 160 (e.g., an ITTFlowtronex pump system with Nexus communication capability) via wired orwireless communications line 162 to obtain data for the water pumpadjustment interface (step 170). The water pump station 160 measures andstores its power usage from a power source 164 at different flow rates(i.e., different rates that water is pumped through the pump station 160and through water line 20, step 172). In this respect, the pump station160 creates and maintains a power efficiency profile for the pump 160and then communicates this information to the central controllersoftware. Since the efficiency of pump stations 160 tends to change overtime (e.g., become less efficient at certain pump speeds with wear,tear, dirt, etc.), the efficiency profile is periodically sent to thecentral controller software.

In step 174, the software stores the efficiency profile data (e.g. in adatabase) and displays the corresponding data on the water pumpadjustment interface 150. Returning to FIG. 6, the power efficiencyprofile data can be displayed in the KW/hour display 159 that isassociated with each slider 154, displaying rate of power usage and thecost of the power usage (assuming an electricity rate cost is known). Asthe user adjust the slider 154 upward or downward to modify the flowrate, the KW/hour display 159 changes according to the pump profile.Additionally, the pump usage graphs can display data on the efficiencyprofile data in a variety of different ways, such as the rate, cost ortotal amount of electricity for a desired amount of time. In thisrespect, the power usage and electric cost for an irrigation schedulecan be directly managed.

Soil Moisture Sensor Data

The central controller software can accept data from a plurality of soilmoisture sensors located on the irrigated turf. This soil moisture datacan be stored on the server 12 that executes the central controllersoftware or other locations.

FIG. 9 illustrates a soil moisture interface 180 for selectivelydisplaying soil moisture data from the plurality of soil moisturesensors. For example, the user can select which moisture sensor's datais displayed by selecting check boxes 189 in a hierarchical list display188 of available moisture sensors. Data from selected moisture sensorscan be displayed in a variety of different graphs, such as those ingraph display 186, that illustrates several moisture history levels,temperature history levels and salinity history levels. A map display182 can also display the relative location of each moisture sensor bydisplaying moisture sensor icons 184, based on which check box 189 ischecked. Additionally, both the moisture level and an irrigationschedule can be displayed on a single graph, allowing a user to comparethe alignment of the moisture level with the irrigation schedule.

As seen in FIG. 10, the watering plan interface 104 and map displayinterface 182 can also be displayed simultaneously, allowing the user toview the irrigation schedule and the relative locations of soil moisturesensors (or other map items, such as sprinklers).

Flow Interface

As seen in FIG. 11, the central control software also includes a flowinterface 190 that displays a flow graph 192 showing past flow (i.e.,historical water flow) and future flow according to the wateringschedule. Preferably, this flow data is presented in a multicoloredgraph where each color represents flow from different geographiclocations, watering stations, satellite controllers or sprinklers asseen in the legend box 196.

In one example, the graph 192 graphs the gallons per minute versus thetime. The scale interface 194 allows a user to adjust the scale of timeon the graph 192 while the interface buttons 198 control graph updatesand flow recalculations. Alternately, this graph 192 can be displayed onthe same page as the watering plan interface 104, allowing a user toview past watering activity, compare this activity to the irrigationschedule (e.g., to see if a prior user made manual wateringapplications), and see future planned water flow activity.

Demand ET Interface

Preferably, the irrigation software includes a demand evapotranspiration(ET) interface that allows a user to input various ET data such asmaximum demand ET, total area, water allotment, manual ET value, lowtemperature, high temperature, and historic ET values per month. Thisallows the user to limit and customize the maximum amount of water thancan be added to an irrigation schedule due to ET values.

Instant Program Interface

FIG. 12 illustrates an instant program interface 200 which allows a userto create a new watering program via a hierarchical interface 202 to runimmediately or at a later date. Specifically, watering stations areshown in the hierarchical interface 202 (which operates similarly tointerface 108) based on geographic location (e.g., golf course hole).The user can use checkboxes 189 to select irrigation stations and thenuse arrows 206 to move the stations over to the current program window204. Once the user has added all of the desired stations, the currentprogram window 204, the program can be named and either saved or deletedvia interface buttons 205. Once saved, the program can be set to runimmediately or at a future date.

Manual Irrigation

FIG. 13 illustrates a manual irrigation interface 210 that allows a userto manually activate specified irrigation stations (e.g., satellitestations) and their associated sprinklers. The user can make a stationselection via a selection area 212 (similar to previously describedselection area 202 with checkboxes 189) which provides a hierarchicaldisplay 212 based on various aspects such as types of areas (e.g., golftees, fairways, holes, etc.).

Once selected, the interface buttons 206 can be used to copy theselected stations to the manual program window 215 where various programactions can be selected via program buttons 214 (e.g., run, pause, stop,resume, hold, remove hold and length of runtime). Finally, the buttons216 can be used to start or clear the program.

Precipitation Management Groups

FIG. 14 illustrates a station group interface 220 that allows a user tocreate a group of irrigation stations that are associated with eachother (such as golf greens, holes, roughs or other geographiclocations). In this respect, groups of stations can be programmed oradjusted together.

Stations are shown in hierarchical station display 222, allowing forindividual selection via checkboxes 189. Once selected, the stations canbe added, removed or assigned to a group via buttons 226 and willdisplay in a hierarchical station group display 224. When the stationgroupings are properly arranged, the user can a group name in thedesired station group display 224 and apply the groupings with the applybutton 228.

Stations may also be assigned a Precipitation Management Group numbervia the number increment interface 229 that is used by the flowmanagement routine of the irrigation software to manage the applicationrate of water. This control is used to limit stations from running atthe same time as other stations. In this respect, the rate ofprecipitation for multiple sprinklers from a geographic area can befine-tuned to reduce possible runoff of the water (i.e., deliveringwater faster than the turf can absorb).

Rain Schedule Adjustment

Preferably, the central controller software also includes a feature toadjust or delay an irrigation schedule in the event of rain as seen inthe flow chart of FIG. 15. In 230, rain is detected (e.g., by a rainsensor or weather station in communication with the server 12).

In 232, any active watering events (i.e., a length of time a station isprogrammed to irrigate) of the irrigation schedule are terminated. Allfuture watering events have their start time immediately andperiodically recalculated to a later time, but the end time of eachirrigation event of the irrigation schedule is maintained, as seen in234. Preferably, this calculation reduces the scheduled duration of theirrigation events based on an amount equal to the rain fall that hasbeen received at that point in time. For example, if one inch of rainhas fallen, the irrigation event's start time is reduced by an amount oftime equal to irrigate one inch of rain.

If the rain is still falling at the recalculated start time for awatering event in the schedule, the start time (but not the end time) isfurther recalculated to a later time and the duration of the wateringevent is further reduced, as seen in 236. As seen in 238, this patterncontinues until the rain stops, the originally scheduled duration hasbeen completely satisfied by the received rain fall or the “anchored”irrigation end time passes.

Map To Second Monitor Button

As seen in FIG. 10, the irrigation software interface includes a mapdetachment button 181 that removes or hides the map display 182 from thecurrent interface view and displays the map display 182 on a secondmonitor connected to the same server 12. In other words, the mapdetachment button causes the map display 182 to “move over” to a secondmonitor that may be attached to the server 12. This function allows auser to view a greater amount of data from another interface (e.g.,watering plan interface 104) which may span the entire first monitor,while the entire second monitor can display the geographic irrigationmap.

Start Time Shift

Returning to FIG. 2, the irrigation software preferably includes a starttime shift interface 107 that allows a user to shift the start times forall watering events for a schedule forward or backward in time. Theinterface 107 preferably includes a time input window for specifying theamount of time to shift all watering events and forward/backward buttons107B for executing forward or backward time shift. Hence, the user caneasily and quickly shift all watering event times without directlymodifying the relatively complex irrigation schedule.

Conditional Screen Saver

FIGS. 16 and 17 illustrate a computer monitor 50 that displays aconditional screen saver based on the rain/hold state of the irrigationsoftware. When rain, site use, maintenance or a similar an event occurs,an irrigation software user may decide to halt or “hold” an irrigationschedule until the rain or event stops (e.g., by pressing a “hold”button on the software interface). Often, a user may forget that theirrigation schedule has been set to hold or stop all irrigation andtherefore may inadvertently prevent irrigation for a longer period oftime than desired.

The conditional screen saver helps alert the user to hold status of theirrigation software by displaying several screen savers on the server 12based on the hold status. For example, screen saver 250 may indicatethat the irrigation schedule hold is off, allowing normal irrigation.This screen saver may be a company logo, a sun or even a text messageindicating the hold status. Screen saver 252 may indicate that theirrigation schedule hold is on, preventing normal irrigation accordingto the schedule. This screen saver may be a raining cloud, a circle witha diagonal line through it or a text message indicating the hold status.

When a user modifies the hold status, the irrigation software preferablychanges the operating systems screen saver functionality to include thedesired text or graphics. Therefore, the server 12 can operate accordingthe screen saver of the rules of the operating system (e.g., Windows,Mac or Linux) while communicating the hold status of the irrigationsoftware.

Although the invention has been described in terms of particularembodiments and applications, one of ordinary skill in the art, in lightof this teaching, can generate additional embodiments and modificationswithout departing from the spirit of or exceeding the scope of theclaimed invention. Accordingly, it is to be understood that the drawingsand descriptions herein are proffered by way of example to facilitatecomprehension of the invention and should not be construed to limit thescope thereof.

1. An irrigation system comprising central controller software.
 2. Amethod of irrigating using central controller software.
 3. An irrigationsystem comprising a user interface.